2.0 5.3.2.1 Manage Field Activities and Field Orders

Reference: Stop Premise Based Service Process Model - Page 1 for the associated business process diagram.

Actor/Role: CSR - CC&B

Description: If fieldwork is required, a Field Activity is created. The Field Activity Type is configured based on specific profiles. Each Field Activity eligible for dispatch will have a specific Dispatch Group defined for every Service Point Type and Operations Area. The SA type SA/SP Fieldwork Creation algorithm determines if a Field Activity is necessary. The background process, Pending SA/SP Monitor, creates Field Activities for Pending Start and Stop Agreements shortly before the start/stop date if Field Activities have not already been created. Once the Field Activity is completed the start read is made available in CC&B. The background process, Service Agreement Activation, uses this Field Activity information to determine if the Pending Service Agreement can be activated. Refer to 5.3.2.1 Manage Field Activities and Field Orders.

Process Name

•	Pending SA/SP Monitor - PSASPM - Creates field activities shortly before the start/stop date if field activities have not already been created.

•	FANRMRCO - The complete field activity using a recent read process looks for pending start / stop field activities for a meter read recently. It prorates the read into an end read and starts read for the start and stop SA's.

•	FA Completion - FACOMPL - The field activity completion process completes field activities and field orders using the records in the various field activity staging tables.

•	SASP - The find read for SA/SP process updates SA/SP records of active service agreements with the appropriate start or stop read.

Entities to Configure

•

FA Types

•	FA Type Profiles

•	Operations Area

•	Dispatch Group

•	Field Service Class

•	Field Service Control

•

FA Remark

Business Objects

•	C1-ServiceRequestIntegration - This business object is used as a parent service task type BO for service request related task type BOs.

•	C1-NotifyAppointmentTaskType - This business object is used to capture the To Do Type and optional Role to use for appointment notification.

•	C1-NotifyMissedApptTaskType - This business object is used to capture the Adjustment Type to use for missed appointment compensation.

•	C1-CreateCustContactTaskType - Service Task Type BO for Customer Contact Notification.

•	C1-ServiceRequestTask - This parent business object defines the behavior of certain service requests.

•	C1-NotifyAppointmentTask - This business object defines the behavior of an appointment notification update request in the service request integration.

•	C1-NotifyMissedAppointmentTask - This business object defines the behavior of a missed appointment notification update request in the service request integration.

•	C1-CreateCustomerContactTask - This business object defines the behavior of a customer contact creation update request in the service request integration.